`vkFrameBoundaryANDROID` is a non-standard Vulkan call (it does
not belong to the core nor to any registered extension) used by
some Android applications to present a `AHardwareBuffer` to the
screen.
In particular, Android UI applications present to the screen
using this call.

Currently, when the call is simply forwarded to the driver when
encountered by the replayer.
The issue is that this call only actually presents to the screen
when a `AHardwareBuffer`-bound image is submitted. However, at
replay time, the `AHardwareBuffer` is often (always, as far as I
encountered) impossible to recreate in the exact same way - and
the issue gets worse when replaying on a different platform.
Thus, even if the image is properly rendered and the call
forwarded, the screen remains black - even on the exact same
device.

This commit tries to fix this by considering the
`vkFrameBoundaryANDROID` call like an additional
`vkQueuePresentKHR` call.
The call is treated by the polymorphic `VulkanSwapchain` that
decides whether to create a window a present to it (virtual
swapchain behavior) or forward the call (offscreen/default
swapchain behavior).

Change-Id: If3dc05d52824547b14c0fe0c35311d4764c98826

- properly handle multiple devices and allow to cleanup adhoc resources.

the VulkanSwapchain::Clean() method override was not possible, because it is invoked
after all devices are already destroyed.
so this required to add a virtual VulkanSwapchain::CleanDeviceResources(VkDevice)
and attach that in VulkanReplayConsumerBase::OverrideDestroyDevice and FreeAllLiveObjects.

…se FIFO instead